@forki FYI

$ ./build.sh Default

Starting download from https://github.com/fsprojects/Paket/releases/download/3.3.2/paket.exe

Done.

Paket version 3.3.2.0

Paket failed with:

    Error in paket.dependencies line 33

  Package xunit.runners is defined more than once in group Main of /home/travis/build/fsharp/FAKE/paket.dependencies

if you're still having build issues try it with these settings in your project.json

{
  "name": "",
  "version": "1.0.0-*",
  "buildOptions": {
    "compilerName": "fsc",
    "compile": {
      "includeFiles": [

      ]
    }
  },
  "dependencies": {
    "Microsoft.FSharp.Core.netcore": "1.0.0-alpha-160509",
    "FSharp.Compiler.Service.netcore": "1.0.0-alpha-00001",
    "FSharp.Compiler.Service.ProjectCracker.netcore": "1.0.0-alpha-00001",
    "NETStandard.Library": "1.5.0-rc2-24027"
  },
  "tools": {
    "dotnet-compile-fsc": {
      "version": "1.0.0-*",
      "imports": [
        "dnxcore50",
        "portable-net45+win81",
        "netstandard1.3"
      ]
    }
  },
  "frameworks": {
    "netstandard1.5": {
      "imports": [
        "portable-net45+win8",
        "dnxcore50"
      ]
    }
  }
}

and these in your nuget.config

<?xml version="1.0" encoding="utf-8"?>
<configuration>
  <packageSources>
    <!--To inherit the global NuGet package sources remove the <clear/> line below -->
    <clear />
    <add key="dotnet-core" value="https://dotnet.myget.org/F/dotnet-core/api/v3/index.json" />
    <add key="dotnet-cli" value="https://dotnet.myget.org/F/dotnet-cli/api/v3/index.json" />
    <add key="cli-deps" value="https://dotnet.myget.org/F/cli-deps/api/v3/index.json"/>   
    <add key="fsharp-daily" value="https://www.myget.org/F/fsharp-daily/api/v3/index.json" />    
    <add key="fsharp-compiler-service" value="https://ci.appveyor.com/nuget/fsgit-fsharp-compiler-service"/>
    <add key="api.nuget.org" value="https://api.nuget.org/v3/index.json" />
  </packageSources>
</configuration>

@cloudRoutine Build is fine net46 and netcoreapp1.0 (the AppVeyor/Travis issue is unrelated). Running in net46 works as well. Only running Fake.netcore with netcoreapp1.0 is broken. I think I have most of the stuff already added to project.json and NuGet.config, but I will look again later, thanks.

Updated first post with the current errors I'm encountering...
Seems like I build FSharp.Compiler.Service wrong?
IIRC I did just build DotnetCliBuild and then copied the resulting nuget package FSharp.Compiler.Service.netcore.1.0.0-alpha-00001.nupkg to this branch.

@cloudRoutine I switched to the myget feed which contains FSharp.Compiler.Service (and deleted local nuget caches). Sadly the same thing happens. Thanks again for the tipp.

@matthid I managed to get it to run, but I had to remove some dependencies and functionality. You'll need to find compatible versions to work with what's here or try another implementation approach.

Fake.netcore
Fakelib.netcore

It's a pain to do, but you can usually find the sources of conflict in the project.lock.json

@cloudRoutine with dotnet version are you using?

$ dotnet --version
1.0.0-preview1-002702

It's already working for me (at least after running dotnet publish, see first post). It just seems there are some bugs in FSharp.Compiler.Service.netcore

dotnet --version
1.0.0-preview3-003161

i guess you're on top of it then 👍

I have no idea. This whole versioning is so confusing. I have no idea if I should upgrade and try do make it work with preview3 or stay on preview1 which is suggested here: https://github.com/dotnet/netcorecli-fsc/wiki

Honestly I'd wait until everything becomes more stable. There's no huge gain in rushing to try to get it done early when it could be done later much faster with less headaches.

Wow... Now I get some internal F# compiler error: error FS0192: internal error: the IL instruction Microsoft.FSharp.Compiler.AbstractIL.IL+ILInstr+I_seqpoint cannot be emitted.

I think I have to give up for now.

@cloudRoutine Yeah I kind of agree for the cli tooling, that's why I have given up on the run -f netcoreapp1.0 thing. But as it "works" after publishing and the runtime should be "stable" now I think it is the time to make FAKE and the FSharp.Compiler.Service ready :).

Most of the errors now are probably FCS specific bugs and I'm not sure anyone has interest in fixing them (if not FAKE).

Related: fsharp/fsharp-compiler-docs#593 (you need those changes for this branch)

Wow I made it work:

$ cat test.fsx
printfn "Hello FAKE"

$ dotnet exec bin/Debug/netcoreapp1.0/publish/Fake.netcore.dll run --verbose test.fsx
FakePath: C:\PROJ\FAKE\src\app\Fake.netcore\bin\Debug\netcoreapp1.0\publish\FakeLib.netcore.dll
FAKE - F# Make "4.29.2"
Running Buildscript: test.fsx
Cache doesn't exist
FAKE: Trying to resolve FSharp.Compiler.Service.netcore.resources, Version=1.0.0.0, Culture=en-US, PublicKeyToken=null
FAKE: Trying to resolve FSharp.Compiler.Service.netcore.resources, Version=1.0.0.0, Culture=en, PublicKeyToken=null
FAKE: Trying to resolve System.Core, Version=3.5.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089
FAKE: Trying to resolve FSharp.Compiler.Service.netcore.resources, Version=1.0.0.0, Culture=en-US, PublicKeyToken=null
FAKE: Trying to resolve FSharp.Compiler.Service.netcore.resources, Version=1.0.0.0, Culture=en, PublicKeyToken=null
Hello FAKE
Caching is disabled on CoreCLR, see https://github.com/dotnet/coreclr/issues/919#issuecomment-219212910
Ready.

Updated first post, updated to latest preview 2 tooling and changed to Argu for command line parsing.

I made a first release for win7 to check how bootstrapping could look like: https://github.com/matthid/FAKE/releases/tag/v1.0-alpha-01

How I'm moving this forward and my suggested migration path:

• Creating a new library "FakeLib.Core" which will be the absolute core of what we need to run scripts
• Move existing functionality one by one to new packages and make them reference each other and "FakeLib.Core" (if they need it). The new packages should be usable as libraries if possible (from regular Programs).
• The existing "FakeLib" should reference all the new packages and "FakeLib.Core". This way we can continue delivering the known "Fake" (the package will just contain more files). We just need to make sure that #r "FakeLib.dll" still loads all files. (needs to be tested, if not we can create the "old" FakeLib by using ILMerge)
• Once everything is converted we could in theory get rid of "FakeLib" and write a new console application using the new packages, while providing the "old" command-line interface. This would print a warning to the user to update Fake to the dotnetcore version.

This is the general Roadmap. For now I'm concentrating on the bootstrap experience and to get the most important features converted to separate packages.

The road so far:

• Released https://github.com/matthid/FAKE/releases/tag/core-v1.0-alpha-02

• Run simple scripts without dependencies

• Fake is now capable of restoring dependencies before running the build script. You can specify dependencies within your build script in a Fake Dependencies section.

• Either embed your dependencies, like:

  (* -- Fake Dependencies paket-inline
  source https://nuget.org/api/v2
  
  nuget System.Xml.XmlDocument ~> 4.0
  nuget System.Security.Cryptography.Algorithms ~> 4.0
  nuget Microsoft.FSharp.Core.netcore
  -- Fake Dependencies -- *)
  #load "./.fake/unusedDependencies.fsx/loadDependencies.fsx"
  
  open System.Xml
  
  printfn "Starting Build."
  

• Or use an external paket.dependencies file:

  (* -- Fake Dependencies paket.depedencies
  file ./paket.dependencies
  group Main
  -- Fake Dependencies -- *)
  #load "./.fake/use_external_dependencies.fsx/loadDependencies.fsx"
  
  
  printfn "Starting Build."
  

  Note the typo "paket.depedencies" in the header. This will be fixed in the next version. Note also the "./" in the file specifier, this is currently required as well.

• The command line is using Argu 3 and SubCommands (fake.netcore.exe run is for running scripts, just look into the --help output). I'm thinking about adding more sub-commands in the future.

• The loadDependencies.fsx file is currently empty. It will be used to provide nice editor support for editing scripts in the future (it is not required/use by fake).

Somehow related a set of helpers to run dotnet.exe commands from FAKE:

https://github.com/dolly22/fake.dotnet

I'm also having a wild idea: since there are so many FAKE extensions (in separate packages), maybe we could study a ExtensionTypeProvider which takes care of downloading the package and exposing the helpers to the FAKE Script?

https://github.com/dotnet/cli/issues/6465

Its incredible what changes were necessary throughout the ecosystem to make this possible. When I started it I thought we just integrate paket and things would work :)

After almost a year this is finally green. This means we can finally look at FAKE instead of fixing all the other stuff.

This also means I will now work on branches on top of this and then merge them back here for the time being. Sadly this is less visible for others until we have the access rights figured out.

#1559